Translate Solution Content

Learn how to export content for translation, edit translation files, and import the files back to Visier.

Who can use this feature?

Users with this profile additional capability: 

  • Translation

Not sure if you have this feature or capability? Reach out to your administrator.

Prerequisites: Set your user language preferences to the language you are authoring in.

Authoring translatable content

You must create content in one language per project.

If you author in multiple languages in one project, content may be missed in the translation export because you must select a single source language when exporting the project changes.

Example:  

You and a colleague are authoring analyses in the same project, but your language is French and your colleague's language is English. You authored Analyses 1 (French) and your colleague authored Analysis 2 (English).

After committing the changes to your project, you export the translation strings and select the following settings:

  • Source language: French
  • Target language: English

The export will contain all the content authored in French and the returned strings after translation will be in English. However, Analysis 2 doesn't contain French strings because it was authored in English, so it won't be included in the translation export.

Additionally, if you change your language preference and return to your project that was authored in a different language, you may unintentionally overwrite your existing content in the project.

Caution: This may overwrite all content in the project! Ensure that you're authoring in one language per project.

Language-specific content is stored in objects, that is, if you only author an analysis in English, the French object for that same analysis is empty. If you change your language, Visier attempts to populate empty objects with available content so that every object has an identifiable display name.

By authoring in multiple languages in one project, you may overwrite existing content.

Example:  

You are authoring an analysis in French. You leave the project and change your language preference to English. If you return to the project, Visier will show you English-language content. However, your analysis was authored in French, so the English object for that analysis is empty. Because the French object contains authored content, Visier duplicates that content into the English object so that the analysis has an identifiable display name. Additionally, in the project, every content object has been overwritten, including the ones that had existing content.

Exporting changes for translation

After authoring content in a source language, you can export the project changes to translate them into another language. You can also export all the translatable content in the production project. The export includes a ZIP file with a directory structure of all the modules, such as Organization and Talent, with a XLIFF translation file per folder, as well as any HTML or SVG files that might be associated with the content.

Note:  

  • Objects without a module can be found in the NO_MODULE directory.
  • The module’s symbol name is used for the exported directory name.

To export solution content for translation:

  1. In a project, on the navigation bar, click Model > Settings > Translation.
  2. To export translatable content, do one of the following:

    Option

    Do this

    Export the project’s unpublished committed changes.

    • Click Export Project Changes.

    Export content that has changed between two production versions.

    1. Click Export Content Changes.
    2. In the After box, select an updated production version from the list. Content changes up to and including this production version will be exported.
    3. In the Before box, select a base production version from the list. Content changes from this production version will not be included in the export but will be used as a baseline for comparison.

    Export all content that exists in production.

    • Click Export Production. This option is recommended for first time translations.

    Export only the untranslated production content.

    • Click Export Production (Un-Translated Only). This option is recommended for subsequent translations.
  3. Select a source locale. This is the language that you authored the content in.
  4. Select a target locale. This is the language that the source content will be translated into.
  5. Click Export.

    Result: A ZIP file containing the translation files is downloaded to your computer.

Editing translation files

Note: If you leave any of the content untranslated, the content will default to showing the original English text.

After you've exported the content for translation, a ZIP file containing the translation files is downloaded to your computer. The file contains a directory structure of all the modules, such as Organization and Talent, with a XLIFF translation file per folder, as well as any HTML or SVG files that might be associated with the content. To start editing the files for translation, unzip the compressed file.

Editing XLIFF files

  1. In the unzipped file, locate the folder for the module you want to translate.
  2. Open the XLIFF file in a text editor or a Computer-Assisted Translation (CAT) tool.

  3. At the top of the file, ensure the correct source and target language codes are listed. For example,source-language="en" and target-language="fr".

    Target Language

    Code

    English - United States

    en

    French

    fr

    German

    de

    Portuguese - Brazil

    pt

    Spanish - Mexico

    es

    Spanish - Spain

    es-ES

    Note: If you selected No Target during the translation export, the target language code will not be listed in the XLIFF file. You must manually add the target-language attribute to the <file> tag as shown below:

    <file date="1755636420764" original=" D3M Base V1.9.14" source-language="en" target-language="fr">

  4. Insert the translated text. For each segment of text you need to translate, you'll see a <source> tag containing the original text. You must insert the translated text inside the corresponding <target> tag. If there is no <target> tag, you must manually add it.

The below examples show a XLIFF file before and after the target language code and translated text has been added.

Copy
Example: Before translation
<?xml version="1.0" encoding="UTF-8"?>
<xliff>
    <file date="1634057639659" original=" Core Blueprint V1.16.7" source-language="en">
        <body>
            <trans-unit id="3f2abea4-2a6b-4911-8bb8-4f48cb867aa8" resAttributeName="DisplayName" resname="positionRemovedInPeriod" restype="metric">
                <source>Managed Positions Removed in Period</source>
                <note>The total number of removed positions during the period.</note>
            </trans-unit>
        </body>
    </file>
    <blob-dictionary/>
</xliff>
Copy
Example: After translation
<?xml version="1.0" encoding="UTF-8"?>
<xliff>
    <file date="1634057639659" original=" Core Blueprint V1.16.7" source-language="en" target-language="fr">
        <body>
            <trans-unit id="3f2abea4-2a6b-4911-8bb8-4f48cb867aa8" resAttributeName="DisplayName" resname="positionRemovedInPeriod" restype="metric">
                <source>Managed Positions Removed in Period</source>
                <target>Postes supprimés sur la période</target>
                <note>The total number of removed positions during the period.</note>
            </trans-unit>
        </body>
    </file>
    <blob-dictionary/>
</xliff>

Editing HTML and SVG files

If your export includes HTML or SVG files, you must also translate any text within them. After you edit these files, you must add the correct language code to the file name and save the translated versions in the same folder as the corresponding XLIFF file. As well as edit the file name in the <value> tag in the XLIFF file.

For example, if you're translating the English file Html3.html into French, you would:

  1. Rename the file from Html3.html to Html3-fr.html and save it in the same folder as the XLIFF file.
  2. Open the corresponding XLIFF file in a text editor or a Computer-Assisted Translation (CAT) tool.
  3. In the XLIFF file, locate the <dictionary-node> that contains your file name in the <key> tag.
  4. In the <value> tag, update the file name to include the French language code. For example, change 0a2be88d-9efa-4dd8-9e80-f9a30a953540--metric--en.html is changed to 0a2be88d-9efa-4dd8-9e80-f9a30a953540--metric--fr.html.

Note: It is crucial to add the correct language code to both the file name in the folder and in the <value> tag in the XLIFF file. This ensures the new translated file is not overwritten by the original English file.

Importing translated files

Visier allows you to import translation files after the content is translated.

The imported file must be a compressed ZIP file that reflects the original directory structure and file names of the exported ZIP file with the updated strings in each of the translated files.

Note: The directory structure must have at least one translation file in each folder. If there’s an empty folder or a folder without a translation file, you must manually delete the folder before importing.

Compress the directory structure at the top-level folder so that the directory reflects the original structure of the exported translation. The ZIP file name is not required to be the same as the original file name from the export.

Visier expects the following folder structure in your ZIP file:

  • Top-level folder. For example, “Visier_Translation_And_Blobs”.
    • Module-level folders. For example, “Organization”.
      • Translation files. For example, “Visier_Translation.xlf”.

To import translation files:

  1. In a project, on the navigation bar, click Model > Settings > Translation.
  2. Click Import.
  3. Select the ZIP file.
  4. Click Upload File.
  5. On the navigation bar, click the Home button > Changes. You should see a change for each translation.
  6. Commit the changes to the project.

To validate the imported content, do one of the following:

Option

Do this

Validate by viewing translations in Settings
  1. In a project, on the navigation bar, click Model > Settings > Translation.
  2. Click View Imported Translations.
  3. In the Select drop-down list, select the target language.

Validate by previewing the solution in Studio
  1. In the global navigation bar, in the upper-right corner, click your username.
  2. Click Preferences.
  3. Change your user preferences to the target language.
  4. Return to your project.
  5. On the navigation bar, click Preview Solution.